Blockchain-Based Digital Token Utilization

ABSTRACT

Methods, systems, and apparatuses for blockchain-based digital token utilization are described herein. Data corresponding to digital tokens may be stored on a blockchain associated with a decentralized peer-to-peer (P2P) network. Smart contracts for collecting digital tokens in exchange for service provider tokens may be deployed to the blockchain. Smart contracts for distributing digital tokens based on credit tokens may be deployed to the blockchain. Through execution of the smart contracts, digital tokens may be utilized by users in various ways.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to patentapplication Ser. No. 15/967,064 entitled “Blockchain-Based Digital TokenUtilization” and filed on Apr. 30, 2018, which is incorporated byreference in its entirety.

FIELD

Aspects described herein generally relate to decentralized peer-to-peer(P2P) computer systems specialized for the purpose of managing ablockchain. In particular, one or more aspects of the disclosure relateto utilizing digital tokens on or using a blockchain.

BACKGROUND

Centralized computing systems may be used to manage information relatedto digital tokens. Centralized computing systems may receive digitaltokens from a plurality of entities, and may control the distribution ofthe digital tokens to users of the centralized system in return forinterest provided by the users. But centralized computing systems mayconstitute a single point of failure, which may be undesirable from areliability standpoint and from a security standpoint.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify required or critical elements or to delineate the scope ofthe claims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein aredirected towards utilizing digital tokens on a blockchain.

In accordance with one or more embodiments, a computing platformconfigured to operate in a decentralized peer-to-peer (P2P) network andincluding one or more processors and memory storing at least a portionof a blockchain of the decentralized P2P network may receive, from afirst user computing device, a first registration request forregistering a collection smart contract. The computing platform mayregister the collection smart contract by adding a first new block tothe blockchain. The first new block may comprise the collection smartcontract. The computing platform may receive, from the first usercomputing device, a first event message indicating a first amount ofservice provider tokens, an identifier of the collection smart contract,and a digital signature associated with the first user computing device.The computing platform may verify an authenticity of the first eventmessage based on the digital signature associated with the first usercomputing device. The computing platform may, in response to receivingthe first event message, execute the collection smart contract, whichmay cause the computing platform to transfer, from a service providertoken holder associated with the first user computing device and to thecollection smart contract, the first amount of the service providertokens. The computing platform may receive, from a second user computingdevice, a second event message indicating a first amount of digitaltokens, an identifier of the collection smart contract, and a digitalsignature associated with the second user computing device. Thecomputing platform may verify an authenticity of the second eventmessage based on the digital signature associated with the second usercomputing device. The computing platform may, in response to receivingthe second event message, execute the collection smart contract, whichmay cause the computing platform to transfer, from a digital tokenholder associated with the second user computing device and to thecollection smart contract, the first amount of the digital tokens.Execution of the collection smart contract may cause the computingplatform to determine, based on the first amount of the digital tokensand an exchange rate between the digital tokens and the service providertokens, a second amount of the service provider tokens. Execution of thecollection smart contract may cause the computing platform to transfer,from the collection smart contract and to a service provider tokenholder associated with the second user computing device, the secondamount of the service provider tokens.

In some embodiments, the computing platform may receive, from the seconduser computing device, a third event message indicating a third amountof the service provider tokens and an identifier of the collection smartcontract. The computing platform may, in response to receiving the thirdevent message, execute the collection smart contract, which may causethe computing platform to transfer, from the service provider tokenholder associated with the second user computing device and to thecollection smart contract, the third amount of the service providertokens. Execution of the collection smart contract may cause thecomputing platform to determine, based on an appreciation rateassociated with the digital tokens and a time period between receivingthe second event message and receiving the third event message, anupdated exchange rate between the digital tokens and the serviceprovider tokens. Execution of the collection smart contract may causethe computing platform to determine, based on the third amount of theservice provider tokens and the updated exchange rate between thedigital tokens and the service provider tokens, a second amount of thedigital tokens. Execution of the collection smart contract may cause thecomputing platform to transfer, from the collection smart contract andto the digital token holder associated with the second user computingdevice, the second amount of the digital tokens.

In some embodiments, the computing platform may receive, from the firstuser computing device, a second registration request for registering adistribution smart contract. The computing platform may register thedistribution smart contract by adding a second new block to theblockchain. The second new block may comprise the distribution smartcontract. The computing platform may receive, from the first usercomputing device, a fourth event message indicating a third amount ofthe digital tokens and an identifier of the distribution smart contract.The computing platform may, in response to receiving the fourth eventmessage, execute the distribution smart contract, which may cause thecomputing platform to transfer, from a digital token holder associatedwith the first user computing device and to the distribution smartcontract, the third amount of the digital tokens. The computing platformmay receive, from a third user computing device, a fifth event messageindicating a first amount of credit tokens and an identifier of thedistribution smart contract. The computing platform may, in response toreceiving the fifth event message, execute the distribution smartcontract, which may cause the computing platform to transfer, from acredit token holder associated with the third user computing device andto the distribution smart contract, the first amount of the credittokens. Execution of the distribution smart contract may cause thecomputing platform to determine, based on the first amount of the credittokens and an exchange rate between the digital tokens and the credittokens, a fourth amount of the digital tokens. Execution of thedistribution smart contract may cause the computing platform totransfer, from the distribution smart contract and to a digital tokenholder associated with the third user computing device, the fourthamount of the digital tokens.

In some embodiments, the computing platform may receive, from the thirduser computing device, a sixth event message indicating a fifth amountof the digital tokens and an identifier of the distribution smartcontract. The computing platform may, in response to receiving the sixthevent message, execute the distribution smart contract, which may causethe computing platform to determine, based on the fourth amount of thedigital tokens, a time period between receiving the fifth event messageand receiving the sixth event message, and an interest rate associatedwith the digital tokens, an expected amount of the digital tokens.Execution of the distribution smart contract may cause the computingplatform to, in response to determining that the fifth amount of thedigital tokens corresponds to the expected amount of the digital tokens,transfer, from the distribution smart contract and to the credit tokenholder associated with the third user computing device, the first amountof the credit tokens and an additional amount of the credit tokens.Execution of the distribution smart contract may cause the computingplatform to transfer, from the digital token holder associated with thethird user computing device and to the distribution smart contract, thefifth amount of the digital tokens.

In some embodiments, the computing platform may, in response todetermining that the fifth amount of the digital tokens does notcorrespond to the expected amount of the digital tokens, transfer, fromthe distribution smart contract and to a credit token holder associatedwith the first user computing device, the first amount of the credittokens. In some embodiments, the computing platform may, in response toreceiving the second event message, transfer, from the collection smartcontract and to the distribution smart contract, a portion of the firstamount of the digital tokens. In some embodiments, the computingplatform may determine, based on a credit score associated with thethird user computing device, a second amount of the credit tokens. Thecomputing platform may assign the second amount of the credit tokens tothe credit token holder associated with the third user computing device.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative example of centralized computer system inaccordance with one or more illustrative aspects described herein.

FIG. 2 depicts an illustrative example of decentralized P2P computersystem that may be used in accordance with one or more illustrativeaspects described herein.

FIG. 3A depicts an illustrative example of a full node computing devicethat may be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3B depicts an illustrative example of a lightweight node computingdevice that may be used in accordance with one or more illustrativeaspects described herein.

FIG. 4 depicts an illustrative digital token utilization system that maybe used in accordance with one or more example embodiments describedherein.

FIGS. 5A-5H depict an illustrative event sequence for digital tokenutilization in accordance with one or more example embodiments describedherein.

FIG. 6 depicts an illustrative method for digital token utilization inaccordance with one or more example embodiments described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards methods, systems,and apparatuses for blockchain-based digital token utilization. Datacorresponding to digital tokens may be stored on a blockchain associatedwith a decentralized peer-to-peer (P2P) network. Smart contracts forcollecting digital tokens in exchange for service provider tokens may bedeployed to the blockchain. Smart contracts for distributing digitaltokens based on credit tokens may be deployed to the blockchain. Throughexecution of the smart contracts, digital tokens may be utilized byusers in various ways.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

The disclosure provided herein is described, at least in part, inrelation to a decentralized peer-to-peer (e.g., P2P) system specializedfor the purpose of managing a blockchain. The decentralized P2P systemmay be comprised of computing devices that are distributed in multiplelocations across a geographical area as opposed to a single location.The computing devices forming the decentralized P2P system may operatewith each other to manage a blockchain, which may be a data structureused to store information related to the decentralized P2P system. Morespecifically, the blockchain may be a chronological linkage of dataelements (e.g., blocks) which store data records relating to thedecentralized computing system.

A user may access the decentralized P2P system through a specialized“wallet” that serves to uniquely identify the user and enable the userto perform functions related to the decentralized P2P network. Throughthe wallet, the user may be able to hold tokens, funds, and/or any otherasset associated with the decentralized P2P system. Furthermore, theuser may be able to use the wallet to request performance ofnetwork-specific functions related to the decentralized P2P system suchas fund, token, and/or asset transfers. The various computing devicesforming the decentralized P2P computing system may operate as a team toperform network-specific functions requested by the user. In performingthe network-specific functions, the various computing devices mayproduce blocks that store the data generated during the performance ofthe network-specific functions and may add the blocks to the blockchain.After the block has been added to the blockchain, the wallet associatedwith the user may indicate that the requested network-specific functionhas been performed.

For example, a user may have a wallet which reflects that the user hasfive tokens associated with the decentralized P2P system. The user mayprovide a request to the decentralized P2P system to transfer the fivetokens to a friend who also has a wallet. The various computing devicesforming the decentralized P2P computing system may perform the requestand transfer the five tokens from the wallet of the user to the walletof the friend. In doing so, a block may be created by the variouscomputing devices of the decentralized P2P computing system. The blockmay store data indicating that the five tokens were transferred from thewallet of the user to the wallet of the friend. The various computingdevices may add the block to the blockchain. At such a point, the walletof the user may reflect the transfer of the five tokens to the wallet ofthe friend, and may indicate a balance of zero. The wallet of thefriend, however, may also reflect the transfer of the five tokens andmay have a balance of five tokens.

In more detail, the decentralized P2P system may be specialized for thepurpose of managing a distributed ledger, such as a private blockchainor a public blockchain, through the implementation of digitalcryptographic hash functions, consensus algorithms, digital signatureinformation, and network-specific protocols and commands. Thedecentralized P2P system (e.g., decentralized system) may be comprisedof decentralized system infrastructure consisting of a pluralitycomputing devices, either of a heterogeneous or homogenous type, whichserve as network nodes (e.g., full nodes and/or lightweight nodes) tocreate and sustain a decentralized P2P network (e.g., decentralizednetwork). Each of the full network nodes may have a complete replica orcopy of a blockchain stored in memory and may operate in concert, basedon the digital cryptographic hash functions, consensus algorithms,digital signature information, and network-specific protocols, toexecute network functions and/or maintain inter-nodal agreement as tothe state of the blockchain. Each of the lightweight network nodes mayhave at least a partial replica or copy of the blockchain stored inmemory and may request performance of network functions through theusage of digital signature information, hash functions, and networkcommands. In executing network functions of the decentralized network,such as balance sheet transactions and smart contract operations, atleast a portion of the full nodes forming the decentralized network mayexecute the one or more cryptographic hash functions, consensusalgorithms, and network-specific protocols to register a requestednetwork function on the blockchain. In some instances, a plurality ofnetwork function requests may be broadcasted across at least a portionof the full nodes of the decentralized network and aggregated throughexecution of the one or more digital cryptographic hash functions and byperformance of the one or more consensus algorithms to generate a singlework unit (e.g., block), which may be added in a time-based,chronological manner to the blockchain through performance ofnetwork-specific protocols.

While in practice the term “blockchain” may hold a variety ofcontextually derived meanings, the term blockchain, as used herein,refers to a concatenation of sequentially dependent data elements (e.g.,blocks) acting as a data ledger that stores records relating to adecentralized computing system. Such data records may be related tothose used by a particular entity or enterprise, such as a financialinstitution, and/or may be associated with a particular applicationand/or use case including, but not limited to, cryptocurrency, digitalcontent storage and delivery, entity authentication and authorization,digital identity, marketplace creation and operation, internet of things(e.g., IoT), prediction platforms, election voting, medical records,currency exchange and remittance, P2P transfers, ride sharing, gaming,trading platforms, and real estate, precious metal, and work of artregistration and transference, among others. A “private blockchain” mayrefer to a blockchain of a decentralized private system in which onlyauthorized computing devices are permitted to act as nodes in adecentralized private network and have access to the private blockchain.In some instances, the private blockchain may be viewable and/oraccessible by authorized computing devices which are not participatingas nodes within the decentralized private network, but still have propercredentials. A “public blockchain” may refer to a blockchain of adecentralized public system in which any computing devices may bepermitted to act as nodes in a decentralized public network and haveaccess to the public blockchain. In some instances, the publicblockchain may be viewable and/or accessible by computing devices whichare not participating as nodes within the decentralized public network.

Further, a “full node” or “full node computing device,” as used herein,may describe a computing device in a decentralized system which operatesto create and maintain a decentralized network, execute requestednetwork functions, and maintain inter-nodal agreement as to the state ofthe blockchain. In order to perform such responsibilities, a computingdevice operating as a full node in the decentralized system may have acomplete replica or copy of the blockchain stored in memory, as well asexecutable instructions for the execution of hash functions, consensusalgorithms, digital signature information, network protocols, andnetwork commands. A “lightweight node,” “light node,” “lightweight nodecomputing device,” or “light node computing device” may refer to acomputing device in a decentralized system, which operates to requestperformance of network functions (e.g., balance sheet transactions,smart contract operations, and the like) within a decentralized networkbut without the capacity to execute requested network functions andmaintain inter-nodal agreement as to the state of the blockchain. Assuch, a computing device operating as a lightweight node in thedecentralized system may have a partial replica or copy of theblockchain. In some instances, network functions requested bylightweight nodes to be performed by the decentralized network may alsobe able to be requested by full nodes in the decentralized system.

“Network functions” and/or “network-specific functions,” as describedherein, may relate to functions which are able to be performed by nodesof a decentralized P2P network. In some arrangements, the data generatedin performing network-specific functions may or may not be stored on ablockchain associated with the decentralized P2P network. Examples ofnetwork functions may include “smart contract operations” and “balancesheet transaction.” A smart contract operation, as used herein, maydescribe one or more operations associated with a “smart contract,”which may be one or more algorithms and/or programs stored on ablockchain and identified by one or more wallets and/or public keyswithin a decentralized P2P network. In performing a smart contractoperation, each full node computing device within a decentralized P2Pnetwork may identify a block within a blockchain comprising the smartcontract and, responsive to identifying the block associated with thesmart contract, may execute the one or more algorithms and/or programsof the smart contract. A balance sheet transaction may describe one ormore changes to data holdings associated with one or more nodes within adecentralized network.

In one or more aspects of the disclosure, a “digital cryptographic hashfunction,” as used herein, may refer to any function which takes aninput string of characters (e.g., message), either of a fixed length ornon-fixed length, and returns an output string of characters (e.g.,hash, hash value, message digest, digital fingerprint, digest, and/orchecksum) of a fixed length. Examples of digital cryptographic hashfunctions may include BLAKE (e.g., BLAKE-256, BLAKE-512, and the like),MD (e.g., MD2, MD4, MD5, and the like), Scrypt, SHA (e.g., SHA-1,SHA-256, SHA-512, and the like), Skein, Spectral Hash, SWIFT, Tiger, andso on. A “consensus algorithm,” as used herein and as described infurther detail below, may refer to one or more algorithms for achievingagreement on one or more data values among nodes in a decentralizednetwork. Examples of consensus algorithms may include proof of work(e.g., PoW), proof of stake (e.g., PoS), delegated proof of stake (e.g.,DPoS), practical byzantine fault tolerance algorithm (e.g., PBFT), andso on. Furthermore, “digital signature information” may refer to one ormore private/public key pairs and digital signature algorithms which areused to digitally sign a message and/or network function request for thepurposes of identity and/or authenticity verification. Examples ofdigital signature algorithms which use private/public key pairscontemplated herein may include public key infrastructure (PKI),Rivest-Shamir-Adleman signature schemes (e.g., RSA), digital signaturealgorithm (e.g., DSA), Edwards-curve digital signature algorithm, andthe like. A “wallet,” as used herein, may refer to one or more dataand/or software elements (e.g., digital cryptographic hash functions,digital signature information, and network-specific commands) that allowa node in a decentralized P2P network to interact with the decentralizedP2P network. A wallet may be associated with a public key, which mayserve to identify the wallet. In requesting performance of networkoperations, a private key associated with the wallet may be used todigitally sign the network operation requests.

As will be described in further detail below, a decentralized P2P systemimplementing a blockchain data structure may provide solutions totechnological problems existing in current centralized system constructswith traditional data storage arrangements. For example, conventionaldata storage arrangements that use a central data authority have asingle point of failure (namely, the central storage location) which, ifcompromised by a malicious attacker, can lead to data tampering,unauthorized data disclosure, and exploitation and/or loss of operativecontrol of the processes performed by the centralized system. Theimplementation of a blockchain data structure in a decentralized P2Psystem acts as a safeguard against unreliable and/or malicious nodesacting in the decentralized P2P network to undermine the work efforts ofthe other nodes, e.g., by providing byzantine fault tolerance within thenetwork.

Computing Architectures

FIG. 1 depicts an illustrative example of centralized computer system100 in accordance with one or more illustrative aspects describedherein. Centralized computer system 100 may comprise one or morecomputing devices including at least server infrastructure 110 and usercomputing devices 120. Each of user computing devices 120 may beconfigured to communicate with server infrastructure 110 through network130. In some arrangements, centralized computer system 100 may includeadditional computing devices and networks that are not depicted in FIG.1, which also may be configured to interact with server infrastructure110 and, in some instances, user computing devices 120.

Server infrastructure 110 may be associated with a distinct entity suchas a company, school, government, and the like, and may comprise one ormore personal computer(s), server computer(s), hand-held or laptopdevice(s), multiprocessor system(s), microprocessor-based system(s), settop box(es), programmable consumer electronic device(s), networkpersonal computer(s) (PC), minicomputer(s), mainframe computer(s),distributed computing environment(s), and the like. Serverinfrastructure 110 may include computing hardware and software that mayhost various data and applications for performing tasks of thecentralized entity and for interacting with user computing devices 120,as well as other computing devices. For example, each of the computingdevices comprising server infrastructure 110 may include one or moreprocessors 112 and one or more databases 114, which may be stored inmemory of the one or more computing devices of server infrastructure110. Through execution of computer-readable instructions stored inmemory, the computing devices of server infrastructure 110 may beconfigured to perform functions of the centralized entity and store thedata generated during the performance of such functions in databases114.

In some arrangements, server infrastructure 110 may include and/or bepart of enterprise information technology infrastructure and may host aplurality of enterprise applications, enterprise databases, and/or otherenterprise resources. Such applications may be executed on one or morecomputing devices included in server infrastructure 110 usingdistributed computing technology and/or the like. In some instances,server infrastructure 110 may include a relatively large number ofservers that may support operations of a particular enterprise ororganization, such as a financial institution. Server infrastructure110, in this embodiment, may generate a single centralized ledger fordata received from the various user computing devices 120, which may bestored in databases 114.

Each of the user computing devices 120 may be configured to interactwith server infrastructure 110 through network 130. In some instances,one or more of the user computing devices 120 may be configured toreceive and transmit information corresponding to system requeststhrough particular channels and/or representations of webpages and/orapplications associated with server infrastructure 110. The systemrequests provided by user computing devices 120 may initiate theperformance of particular computational functions such as data and/orfile transfers at server infrastructure 110. In such instances, the oneor more of the user computing devices may be internal computing devicesassociated with the particular entity corresponding to serverinfrastructure 110 and/or may be external computing devices which arenot associated with the particular entity.

As stated above, centralized computer system 100 also may include one ormore networks, which may interconnect one or more of serverinfrastructure 110 and one or more user computing devices 120. Forexample, centralized computer system 100 may include network 130.Network 130 may include one or more sub-networks (e.g., local areanetworks (LANs), wide area networks (WANs), or the like). Furthermore,centralized computer system 100 may include a local network configuredto interlink each of the computing devices comprising serverinfrastructure 110.

Furthermore, in some embodiments, centralized computer system 100 mayinclude a plurality of computer systems arranged in an operativenetworked communication arrangement with one another through a network,which may interface with server infrastructure 110, user computingdevices 120, and network 130. The network may be a system specificdistributive network receiving and distributing specific network feedsand identifying specific network associated triggers. The network mayalso be a global area network (GAN), such as the Internet, a wide areanetwork (WAN), a local area network (LAN), or any other type of networkor combination of networks. The network may provide for wireline,wireless, or a combination wireline and wireless communication betweendevices on the network.

In the centralized computer system 100 described in regard to FIG. 1,server infrastructure 110 may serve as a central authority which managesat least a portion of the computing data and actions performed inrelation to the particular entity associated with server infrastructure110. As such, server infrastructure 110 of centralized computer system100 provides a single point of failure which, if compromised by amalicious attacker, can lead to data tampering, unauthorized datadisclosure, and exploitation and/or loss of operative control of theprocesses performed by the server infrastructure 110 in relation to theparticular entity associated with server infrastructure 110. In such acentralized construct in which a single point of failure (e.g., serverinfrastructure 110) is created, significant technological problems ariseregarding maintenance of operation and data control, as well aspreservation of data integrity. As will be described in further detailbelow in regard to FIG. 2, such technological problems existing incentralized computing arrangements may be solved by a decentralized P2Psystem implementing a blockchain data structure, even wholly within theserver infrastructure 110.

FIG. 2 depicts an illustrative example of decentralized P2P computersystem 200 that may be used in accordance with one or more illustrativeaspects described herein. Decentralized P2P computer system 200 mayinclude a plurality of full node computing devices 210A, 210B, 210C,210D, 210E, and 210F and lightweight node computing devices 250A and250B, which may be respectively similar to full node computing device210 described in regard to FIG. 3A and lightweight node computing device250 described in regard to FIG. 3B. While a particular number of fullnode computing devices and lightweight node computing devices aredepicted in FIG. 2, it should be understood that a number of full nodecomputing devices and/or lightweight node computing devices greater orless than that of the depicted full node computing devices andlightweight node computing devices may be included in decentralized P2Pcomputer system 200. Accordingly, any additional full node computingdevices and/or lightweight node computing devices may respectivelyperform in the manner described below in regard to full node computingdevices 210A-210F and lightweight node computing devices 250A and 250Bin decentralized P2P computer system 200.

Each of full node computing devices 210A-210F may operate in concert tocreate and maintain decentralized P2P network 270 of decentralized P2Pcomputer system 200. In creating decentralized P2P network 270 ofdecentralized P2P computer system 200, processors, ASIC devices, and/orgraphics processing units (e.g., GPUs) of each full node computingdevice 210A-210F may execute network protocols which may cause each fullnode computing device 210A-210F to form a communicative arrangement withthe other full node computing devices 210A-210F in decentralized P2Pcomputer system 200 and thereby create decentralized P2P network 270.Furthermore, the execution of network protocols by the processors, ASICdevices, and/or GPUs of full node computing devices 210A-210F may causefull node computing devices 210A-210F to execute network functionsrelated to blockchain 226 and maintain decentralized P2P network 270.

Lightweight node computing devices 250A and 250B may request executionof network functions related to decentralized P2P network 270. In orderto request execution of network functions, such as balance sheettransaction and/or smart contract operations, processors of lightweightnode computing devices 250A and 250B may execute network commands tobroadcast the network functions to decentralized P2P network 270comprising full node computing devices 210A-210F.

For example, lightweight node computing device 250A may requestexecution of a balance sheet transaction related to decentralized P2Pnetwork 270, which may entail a data transfer from a wallet associatedwith lightweight node computing device 250A to a wallet associated withlightweight node 250B. In doing so, processors of lightweight nodecomputing device 250A may execute network commands to broadcast balancesheet transaction network function request 280 to decentralized P2Pnetwork 270. Balance sheet transaction network function request 280 mayinclude details about the data transfer such as data type and amount, aswell as a data transfer amount to full node computing devices 210A-201Fof decentralized P2P network 270 for executing balance sheet transactionnetwork function request 280. Balance sheet transaction network functionrequest 280 may further include the public key associated with thewallet of lightweight node computing device 250B. Processors oflightweight node computing device 250A may execute digital signaturealgorithms to digitally sign balance sheet transaction network functionrequest 280 with the private key associated with the wallet oflightweight node computing device 250A.

At decentralized P2P network 270, balance sheet transaction networkfunction request 280 may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute balance sheettransaction network function request 280 and maintain inter-nodalagreement as to the state of blockchain 226, processors, ASIC devices,and/or GPUs of full node computing devices 210A-210F may execute networkprotocols to receive broadcast of the network function throughdecentralized P2P network 270 and from lightweight node computing device250A. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute hash functions to generate a digest ofbalance sheet transaction network function request 280. The resultantdigest of balance sheet transaction network function request 280 may, inturn, be hashed with the block hash of the most immediately precedingblock of blockchain 226. Processors, ASIC devices, and/or GPUs of fullnode computing devices 210A-210F may execute consensus algorithms toidentify a numerical value (e.g., nonce) corresponding to the particularexecuted consensus algorithm and related to the digest that combines thedigest of the balance sheet transaction network function request 280 andthe block hash of the most immediately preceding block of blockchain226.

For example, in embodiments in which the consensus algorithm is proof ofwork (e.g., PoW), processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210F may perform a plurality of hashingoperations to identify a nonce that, when hashed with the digest thatcombines the digest of the balance sheet transaction network functionrequest 280 and the block hash of the most immediately preceding blockof blockchain 226, produces a hash of a predetermined alphanumericalformat. Such a predetermined alphanumerical format may include apredetermined number of consecutive alphanumerical characters at apredetermined position within the resultant digest that combines thenonce, digest of the balance sheet transaction network function request280, and block hash of the most immediately preceding block ofblockchain 226.

In embodiments in which the consensus algorithm is proof of stake (e.g.,PoS), a private key associated with one of full node computing devices210A-210F may be pseudo-randomly selected, based on balance sheetholdings associated with the public keys of full node computing devices210A-210F, to serve as the nonce. For example, through execution of thePoS consensus algorithm, full node computing devices 210A-210F areentered into a lottery in which the odds of winning are proportional toa balance sheet amount associated the wallet of each of full nodecomputing devices 210A-210F, wherein a larger balance sheet amountcorresponds to a higher probability to win the lottery. The PoSconsensus algorithm may cause a full node computing device from fullnode computing devices 210A-210F to be selected, and the public key ofthe wallet of the selected full node computing device to be used as thenonce.

In embodiments in which the consensus algorithm is delegated proof ofstake (e.g., DpoS), a group of delegates are chosen from full nodecomputing devices 210A-210F by each of computing devices 210A-210F,wherein full node computing devices 210A-210F are allowed to vote ondelegates based on balance sheet holdings associated with the respectivewallets. Full node computing devices 210A-210F, however, may not votefor themselves to be delegates. Once the group of delegates are chosen,the group of delegates from full node computing devices 210A-210F selecta public key associated with a wallet of one of full node computingdevices 210A-210F to serve as the nonce.

In embodiments in which the consensus algorithm is practical byzantinefault tolerance algorithm (e.g., PBFT), each of full node computingdevices 210A-210F are associated with a particular status and/or ongoingspecific information associated with the respective public key of thefull node computing devices. Each of full node computing devices210A-210F receive a message through decentralized P2P network 270 basedon network protocols. Based on the received message and particularstatus and/or ongoing specific information, each of full node computingdevices 210A-210F perform computational tasks and transmit a response tothe tasks to each of the other full node computing devices 210A-210F. Apublic key of a wallet associated with a particular full node computingdevice from full node computing devices 210A-210F is selected by each offull node computing devices 210A-210F based on the response of theparticular full node computing device best fulfilling criteriadetermined based on the network protocols.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F corresponding to the nonce to create a new block with a blockheader (e.g., block hash), which is a digest that combines the digest ofbalance sheet transaction network function request 280, the block hashof the most immediately preceding block, and the identified nonce.Processors, ASIC devices, and/or GPUs of the full node computing devicefrom full node computing devices 210A-210F may execute network protocolsto add the new block to blockchain 226 and broadcast the new block tothe other full node computing devices in the decentralized P2P network270. In some arrangements, the new block may also be time-stamped at atime corresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may beallowed, per the network protocols, to increase balance sheet holdingsassociated with itself by a predetermined amount. In some arrangements,each of full node computing devices 210A-210F may receive an equalportion of the data transfer amount specified by lightweight nodecomputing device 250A for executing balance sheet transaction networkfunction request 280. After the new block has been added to blockchain226, balance sheet transaction network function request 280 may beconsidered to be executed and the data transfer from the walletassociated with lightweight node computing device 250A to the walletassociated with lightweight node 250B may be registered.

As stated above, in some arrangements, a plurality of network functionrequests may be broadcasted across decentralized network P2P network270. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute network protocols to receive broadcast ofeach of the network functions, including balance sheet transactionnetwork function request 280, through decentralized P2P network 270 andfrom the requesting entities, including lightweight node computingdevice 250A. Processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210F may execute hash functions to generate ahash tree (e.g., Merkle tree) of the requested network functions, whichculminates in a single digest (e.g., root digest, root hash, and thelike) that comprises the digests of each of the requested networkfunctions, including balance sheet transaction network function request280. The root digest of the requested network function may, in turn, behashed with the block hash of the most immediately preceding block ofblockchain 226. Processors, ASIC devices, and/or GPUs of full nodecomputing devices 210A-210B may execute consensus algorithms in themanner described above to identify a nonce corresponding to theparticular executed consensus algorithm and related to the digest thatcombines the root digest of the requested network functions and theblock hash of the most immediately preceding block of blockchain 226.The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines the root digest of the network functionrequests, the block hash of the most immediately preceding block, andthe identified nonce. Processors, ASIC devices, and/or GPUs of the fullnode computing device from full node computing devices 210A-210F mayexecute network protocols to add the new block to blockchain 226 andbroadcast the new block to the other full node computing devices in thedecentralized P2P network 270. In some arrangements, the new block mayalso be time-stamped at a time corresponding to the addition toblockchain 226. Furthermore, as a reward for adding the new block toblockchain 226, the full node computing device from full node computingdevices 210A-210F may be allowed, per the network protocols, to increasea balance sheet holdings amount associated with itself by apredetermined amount. In some arrangements, each of full node computingdevices 210A-210F may receive an equal portion of the data transferamount specified by each of the network function requests. After the newblock has been added to blockchain 226, each of the network functionsrequests, including balance sheet transaction network function request280, may be considered to be executed and the data transfer from theprivate/public key associated with lightweight node computing device250A to the private/public key associated with lightweight node 250B maybe registered.

While the description provided above is made in relation to a balancesheet transaction involving lightweight node computing device 250A andlightweight node computing device 250B, it is to be understood thatbalance sheet transactions are not limited to lightweight node computingdevice 250A and lightweight node computing device 250B, but rather maybe made across any of the full node computing devices and/or lightweightnode computing devices in decentralized P2P system 200.

For another example, lightweight node computing device 250B may requesta smart contract operation related to decentralized P2P network 270,which may facilitate a dual data transfer between a wallet associatedwith lightweight node computing device 250B and a wallet associated withanother node in decentralized P2P network 270, such as lightweight nodecomputing device 250A, based on fulfillment of programmatic conditionsestablished by a smart contract. Processors of lightweight nodecomputing device 250B may execute network commands to broadcast smartcontract operation network function request 290 to decentralized P2Pnetwork 270. Smart contract operation network function request 290 mayinclude details about the data transfer such as data type and amount, aswell as a data transfer amount to full node computing devices 210A-210Fof decentralized P2P network 270 for executing the smart contractcorresponding to smart contract operation network function request 290.Smart contract operation network function request 290 may furtherinclude the public key associated with the smart contract. Processors oflightweight node computing device 250B may execute digital signaturealgorithms to digitally sign smart contract operation network functionrequest 290 with the private key associated with the wallet oflightweight node computing device 250B.

At decentralized P2P network 270, smart contract operation networkfunction request 290 may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute smart contractoperation network function request 290 and maintain inter-nodalagreement as to the state of blockchain 226, processors, ASIC devices,and/or GPUs of full node computing devices 210A-210F may execute networkprotocols to receive broadcast of the network function through adecentralized P2P network 270 and from lightweight node computing device250B. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute hash functions to generate a digest ofsmart contract operation network function request 290. The resultantdigest of smart contract operation network function request 290, inturn, may be hashed with the block hash of the most immediatelypreceding block of blockchain 226. Processors, ASIC devices, and/or GPUsof full node computing devices 210A-210F may execute consensusalgorithms to identify a nonce corresponding to the particular executedconsensus algorithm and related to the digest that combines the digestof smart contract operation network function request 290 and the blockhash of the most immediately preceding block of blockchain 226.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines smart contract operation networkfunction request 290, the block hash of the most immediately precedingblock, and the identified nonce. Processors, ASIC devices, and/or GPUsof the full node computing device from full node computing devices210A-210F may execute network protocols to add the new block toblockchain 226 and broadcast the new block to the other full nodecomputing devices in the decentralized P2P network 270. In somearrangements, the new block may also be time-stamped at a timecorresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may, per thenetwork protocols, increase a balance sheet holdings amount associatedwith itself by a predetermined amount. In some arrangements, each offull node computing devices 210A-210F may receive an equal portion ofthe data transfer amount specified by lightweight node computing device250B for executing smart contract operation network function request290. After the new block has been added to blockchain 226, smartcontract operation request 290 may be considered to be executed and thedata transfer from the wallet associated with lightweight node computingdevice 250B to the public key associated with the smart contract may beregistered.

The smart contract may be configured to hold the data transfer from thewallet associated with lightweight node computing device 250B untilfulfillment of certain predetermined criteria hardcoded into the smartcontract are achieved. The smart contract may be configured such that itserves as an intermediate arbiter between entities within thedecentralized P2P network 270 and may specify details of a dual datatransfer between entities.

For example, the smart contract corresponding to smart contractoperation request 290 may be one or more algorithms and/or programsstored on a block of blockchain 226. The smart contract may beidentified by one or more wallets and/or public keys withindecentralized P2P network 270. Lightweight node computing device 250Bmay transmit smart contract operation network function request 290 todecentralized P2P network 270, which may cause execution of thecorresponding smart contract that facilitates a dual data transferbetween a wallet associated with lightweight node computing device 250Band a wallet associated with another node in decentralized P2P network270, such as lightweight node computing device 250A, based onfulfillment of programmatic conditions established by the smartcontract. In the processes of adding the block comprising smart contractoperation request 290 to blockchain 226, each of full node computingdevices 210A-210F may identify the block within blockchain 226comprising the smart contract, associate the data transfer entailed bysmart contract operation request 290 with the smart contract, andexecute the one or more algorithms and/or programs of the smartcontract. In this instance, given that the smart contract facilitates adual data transfer and that data transfer has yet to be received fromanother node (e.g., lightweight node computing device 250A), each offull node computing devices 210A-210F may execute the smart contractwithout fulfillment of the programmatic conditions established by thesmart contract. Accordingly, the funds transferred by lightweight nodecomputing device 250B may remain in the smart contract until the datatransfer from the other node is also associated with the smart contract.

Moving forward, lightweight node computing device 250A may also requesta smart contract operation related to decentralized P2P network 270,which may conclude the dual data transfer between the wallet associatedlightweight node computing device 250A and the wallet associated withlightweight node computing device 250B. Processors of lightweight nodecomputing device 250A may execute network commands to broadcast thesmart contract operation network function request to decentralized P2Pnetwork 270. The smart contract operation network function request mayinclude details about the data transfer such as data type and amount, aswell as a data transfer amount to full node computing devices 210A-210Fof decentralized P2P network 270 for executing the smart contractcorresponding to the smart contract operation network function request.The smart contract operation network function request may furtherinclude the public key associated with the smart contract. Processors oflightweight node computing device 250A may execute digital signaturealgorithms to digitally sign the smart contract operation networkfunction request with the private key associated with the wallet oflightweight node computing device 250A.

At decentralized P2P network 270, the smart contract operation networkfunction request may be broadcasted to each of full node computingdevices 210A-210F through execution of network protocols by full nodecomputing devices 210A-210F. In order to execute the smart contractoperation network function request and maintain inter-nodal agreement asto the state of blockchain 226, processors, ASIC devices, and/or GPUs offull node computing devices 210A-210F may execute network protocols toreceive broadcast of the network function through a decentralized P2Pnetwork 270 and from lightweight node computing device 250A. Processors,ASIC devices, and/or GPUs of full node computing devices 210A-210F mayexecute hash functions to generate a digest of the smart contractoperation network function request. The resultant digest of the smartcontract operation network function request, in turn, may be hashed withthe block hash of the most immediately preceding block of blockchain226. Processors, ASIC devices, and/or GPUs of full node computingdevices 210A-210F may execute consensus algorithms to identify a noncecorresponding to the particular executed consensus algorithm and relatedto the digest that combines the digest of the smart contract operationnetwork function request and the block hash of the most immediatelypreceding block of blockchain 226.

The identification of the nonce enables processors, ASIC devices, and/orGPUs of the full node computing device from full node computing devices210A-210F to create a new block with a block header (e.g., block hash),which is a digest that combines the smart contract operation networkfunction request, the block hash of the most immediately precedingblock, and the identified nonce. Processors, ASIC devices, and/or GPUsof the full node computing device from full node computing devices210A-210F may execute network protocols to add the new block toblockchain 226 and broadcast the new block to the other full nodecomputing devices in the decentralized P2P network 270. In somearrangements, the new block may also be time-stamped at a timecorresponding to the addition to blockchain 226. Furthermore, as areward for adding the new block to blockchain 226, the full nodecomputing device from full node computing devices 210A-210F may beallowed, per the network protocols, to increase a balance sheet holdingsamount associated with itself by a predetermined amount. In somearrangements, each of full node computing devices 210A-210F may receivean equal portion of the data transfer amount specified by lightweightnode computing device 250A for executing the smart contract operationnetwork function request. After the new block has been added toblockchain 226, the smart contract operation transaction networkfunction request 290 may be considered to be executed and the datatransfer from the wallet associated with lightweight node computingdevice 250A to the public key associated with the smart contract may beregistered.

When the smart contract receives the data value from each of lightweightnode computing device 250A and lightweight node computing device 250B,the execution of the smart contract by each of full node computingdevices 210A-210F may cause transfer of the data value from lightweightnode computing device 250A to lightweight node computing device 250B andthe data value from lightweight node computing device 250B tolightweight node computing device 250A.

For example, lightweight node computing device 250A may transmit thesmart contract operation network function request to decentralized P2Pnetwork 270, which may cause execution of the corresponding smartcontract that facilitates the dual data transfer. In the process ofadding the block comprising the smart contract operation requestprovided by lightweight node computing device 250A to blockchain 226,each of full node computing devices 210A-210F may identify the blockwithin blockchain 226 comprising the smart contract, associate the datatransfer entailed by smart contract operation request of lightweightnode computing device 250A with the smart contract, and execute the oneor more algorithms and/or programs of the smart contract. In thisinstance, given that the smart contract facilitates a dual data transferand that data transfers have been received from lightweight nodecomputing device 250A and lightweight node computing device 250B, eachof full node computing devices 210A-210F may execute the smart contractas fulfillment of the programmatic conditions established by the smartcontract has occurred. Accordingly, the funds allocated to the smartcontract by each of lightweight node computing device 250A andlightweight node computing device 250B may be respectively distributedto the intended counterparty.

While the description provided above was made in relation to lightweightnode computing device 250A and lightweight node computing device 250B,it should be understood that any of the full node computing devices andlightweight node computing devices in decentralized system 200 mayparticipate in the smart contract. Furthermore, it should be understoodthat the smart contract may be able to fulfill dual data transfers inthe manner described above across a plurality of entities entering intothe smart contract. For example, a first plurality of entities may enterinto the smart contract, which may hold the data values for each of thefirst plurality of entities until a second plurality of entities enterinto the smart contract. When each of the first plurality of entitiesand the second plurality of entities have entered, the smart contractmay perform the data transfer. Other smart contracts may be includedwhich include algorithms, programs, and/or computer-executableinstructions which cause the performance of one or more functionsrelated to at least cryptocurrency, digital content storage anddelivery, entity authentication and authorization, digital identity,marketplace creation and operation, internet of things (e.g., IoT),prediction platforms, election voting, medical records, currencyexchange and remittance, P2P transfers, ride sharing, gaming, tradingplatforms, and real estate, precious metal, and work of art registrationand transference.

In comparison to the centralized computing system 100 described inregard to FIG. 1, decentralized P2P computer system 200 may providetechnological advantages. For example, by distributing storage ofblockchain 226 across multiple full node computing devices 210A-210F,decentralized P2P computer system 200 may not provide a single point offailure for malicious attack. In the event that any of the full nodecomputing devices 210A-210F are compromised by a malicious attacker,decentralized P2P computer system 200 may continue to operate unabatedas data storage of blockchain 226 and performance of network processesare not controlled by a singular entity such as server infrastructure110 of centralized computing system 100.

Furthermore, by utilizing blockchain data structure 226, decentralizedP2P system 200 may provide technological improvements to conventionaldecentralized P2P systems in regard to byzantine fault tolerancestemming from an unreliable and/or malicious full node acting indecentralized P2P network 270 to undermine the work efforts of the othernodes. For example, in coordinating action between full node computingdevices 210A-210F in relation to a similar computational task (e.g.,consensus algorithm), a malicious node would need to have computationalpower greater than the combined computational power of each of the otherfull node computing devices in decentralized P2P network 270 to identifythe nonce and thereby be able to modify blockchain 226. As such, thelikelihood that a malicious node could subvert decentralized P2P network270 and enter falsified data into blockchain 226 is inverselyproportional to the total computational power of decentralized P2Psystem 200. Therefore, the greater the total computational power ofdecentralized P2P system 200, the less likely that a malicious nodecould subvert decentralized P2P network 270 and undermine blockchain226.

FIG. 3A depicts an illustrative example of a full node computing device210 that may be used in accordance with one or more illustrative aspectsdescribed herein. Full node computing device 210 may be any of apersonal computer, server computer, hand-held or laptop device,multiprocessor system, microprocessor-based system, set top box,programmable consumer electronic device, network personal computer,minicomputer, mainframe computer, distributed computing environment,virtual computing device, and the like and may operate in adecentralized P2P network. In some embodiments, full node computingdevice 210 may be configured to operate in a decentralized P2P networkand may request execution of network functions and/or execute requestednetwork functions and maintain inter-nodal agreement as to the state ofa blockchain of the decentralized P2P network.

Full node computing device 210 may include one or more processors 211,which control overall operation, at least in part, of full nodecomputing device 210. Full node computing device 210 may further includerandom access memory (RAM) 213, read only memory (ROM) 214, networkinterface 212, input/output interfaces 215 (e.g., keyboard, mouse,display, printer, or the like), and memory 220. Input/output (I/O) 215may include a variety of interface units and drives for reading,writing, displaying, and/or printing data or files. In somearrangements, full node computing device 210 may further comprisespecialized hardware components such as application-specific integratedcircuit (e.g., ASIC) devices 216 and/or graphics processing units (e.g.,GPUs) 217. Such specialized hardware components may be used by full nodecomputing device 210 in performing one or more of the processes involvedin the execution of requested network functions and maintenance ofinter-nodal agreement as to the state of a blockchain. Full nodecomputing device 210 may further store in memory 220 operating systemsoftware for controlling overall operation of the full node computingdevice 210, control logic for instructing full node computing device 210to perform aspects described herein, and other application softwareproviding secondary, support, and/or other functionality which may ormight not be used in conjunction with aspects described herein.

Memory 220 may also store data and/or computer executable instructionsused in performance of one or more aspects described herein. Forexample, memory 220 may store digital signature information 221 and oneor more hash functions 222, consensus algorithms 223, network protocols224, and network commands 225. In some arrangements, digital signatureinformation 221, hash functions 222, and/or network commands 225 maycomprise a wallet of full node computing device 210. Memory 220 mayfurther store blockchain 226. Each of digital signature information 221,hash functions 222, consensus algorithms 223, network protocols 224, andnetwork commands 225 may be used and/or executed by one or moreprocessors 211, ASIC devices 216, and/or GPUs 217 of full node computingdevice 210 to create and maintain a decentralized P2P network, requestexecution of network functions, and/or execute requested networkfunctions and maintain inter-nodal agreement as to the state ofblockchain 226.

For example, in order to create and maintain a decentralized P2Pnetwork, processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 may execute network protocols 225. Execution ofnetwork protocols 225 may cause full node computing device 210 to form acommunicative arrangement with other full node computing devices andthereby create a decentralized P2P network. Furthermore, the executionof network protocols 225 may cause full node computing device 210 tomaintain the decentralized P2P network through the performance ofcomputational tasks related to the execution of network requests relatedto a blockchain such as blockchain 226. As will be described in detailbelow, the execution of such computational tasks (e.g., hash functions222, consensus algorithms 223, and the like) may cause full nodecomputing device 210 to maintain inter-nodal agreement as to the stateof a blockchain with other full node computing devices comprising thedecentralized P2P network.

In order to request execution of network functions, such as balancesheet transactions and/or smart contract operations, processors 211,ASIC devices 216, and/or GPUs 217 of full node computing device 210 mayexecute network commands 225 to broadcast the network function to adecentralized P2P network comprising a plurality of full nodes and/orlightweight nodes. The request may be digitally signed by full nodecomputing device 210 with usage of the private/public key informationand through execution of the digital signature algorithms of digitalsignature information 221.

In order to execute requested network functions and maintain inter-nodalagreement as to the state of a blockchain, processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may executenetwork protocols 224 to receive a broadcast of a requested networkfunction through a decentralized P2P network and from a requestingentity such as a full node or lightweight node. Processors 211, ASICdevices 216, and/or GPUs 217 of full node computing device 210 mayexecute hash functions 222 to generate a digest of the requested networkfunction. The resultant digest of the requested network function, inturn, may be hashed with the block hash of the most immediatelypreceding block of the blockchain. As will be described in furtherdetail below, processors 211, ASIC devices 216, and/or GPUs 217 of fullnode computing device 210 may execute consensus algorithms 223 toidentify a numerical value (e.g., nonce) corresponding to the particularexecuted consensus algorithm and related to the digest that combines thedigest of the requested network function and the block hash of the mostimmediately preceding block of the blockchain. The identification of thenumerical value enables processors 211, ASIC devices 216, and/or GPUs217 of full node computing device 210 to create a new block with a blockheader (e.g., block hash), which is a digest that combines the digest ofthe requested network function, the block hash of the most immediatelypreceding block, and the identified nonce. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may add the newblock to the blockchain based on network protocols 224 and broadcast thenew block to the other nodes in the decentralized P2P network.

As stated above, in some arrangements, a plurality of network functionrequests may be broadcasted across the decentralized network P2Pnetwork. Processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 may execute network protocols 224 to receivebroadcast of each of the network functions through the decentralized P2Pnetwork and from the requesting entities. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may execute hashfunctions 222 to generate a hash tree (e.g., Merkle tree) of therequested network functions, which culminates in a single digest (e.g.,root digest, root hash, and the like) that comprises the digests of eachof the requested network functions. The root digest of the requestednetwork function, in turn, may be hashed with the block hash of the mostimmediately preceding block of the blockchain. Processors 211, ASICdevices 216, and/or GPUs 217 of full node computing device 210 mayexecute consensus algorithms 223 to identify a numerical value (e.g.,nonce) corresponding to the particular executed consensus algorithm andrelated to the digest that combines the root digest of the requestednetwork functions and the block hash of the most immediately precedingblock of the blockchain. The identification of the numerical valueenables processors 211, ASIC devices 216, and/or GPUs 217 of full nodecomputing device 210 to create a new block with a block header (e.g.,block hash), which is a digest that combines the root digest of therequested network functions, the block hash of the most immediatelypreceding block, and the identified nonce. Processors 211, ASIC devices216, and/or GPUs 217 of full node computing device 210 may add the newblock to the blockchain based on network protocols 224 and broadcast thenew block to the other nodes in the decentralized P2P network.

Furthermore, memory 220 of full node computing device 210 may storeblockchain 226. Blockchain 226 may include a blocks 227A, 227B, 227C, .. . 227 n, wherein block 227A represents the first block (e.g., genesisblock) of blockchain 226 and block 227 n represents the most immediateblock of blockchain 226. As such, the blockchain 226, which may be areplica or copy of the blockchain of the decentralized P2P network inwhich full node computing device 210 operates, may be a full or completecopy of the blockchain of the decentralized P2P network. Each of theblocks within blockchain 226 may include information corresponding tothe one or more network functions executed by the decentralized P2Pnetwork. As such, blockchain 226 as stored in memory 220 of full nodecomputing device 210 may comprise the totality of network functionsexecuted by the decentralized network.

FIG. 3B depicts an illustrative example of a lightweight node computingdevice 250 that may be used in accordance with one or more illustrativeaspects described herein. Lightweight node computing device 250 may beany of a personal computer, server computer, hand-held or laptop device,multiprocessor system, microprocessor-based system, set top box,programmable consumer electronic device, network personal computer,minicomputer, mainframe computer, distributed computing environment,virtual computing device, and the like and may operate in adecentralized P2P network. In some embodiments, lightweight nodecomputing device 250 may operate in a decentralized P2P network and maybe configured to request execution of network functions through thedecentralized P2P network. As such, lightweight node computing device250 may be different than full node computing device 210 in that it isnot configured to execute network functions and/or operate to maintain ablockchain of a decentralized P2P network. In other aspects, lightweightnode computing device 250 may have substantially the same physicalconfiguration as full node computing device 210, but may be configuredwith different programs, software, or the like.

Lightweight node computing device 250 may include one or more processors251, which control overall operation of lightweight node computingdevice 250. Lightweight node computing device 250 may further includerandom access memory (RAM) 253, read only memory (ROM) 254, networkinterface 252, input/output interfaces 255 (e.g., keyboard, mouse,display, printer, or the like), and memory 260. Input/output (I/O) 255may include a variety of interface units and drives for reading,writing, displaying, and/or printing data or files. Lightweight nodecomputing device 250 may store in memory 260 operating system softwarefor controlling overall operation of the lightweight node computingdevice 250, control logic for instructing lightweight node computingdevice 250 to perform aspects described herein, and other applicationsoftware providing support and/or other functionality which may or mightnot be used in conjunction with aspects described herein.

In comparison to full node computing device 210, lightweight nodecomputing device 250 might not include, in some instances, specializedhardware such as ASIC devices 216 and/or GPUs 217. Such may be the casebecause lightweight node computing device 250 might not be configured toexecute network functions and/or operate to maintain a blockchain of adecentralized P2P network as is full node computing device 210. However,in certain arrangements, lightweight node computing device 250 mayinclude such specialized hardware.

Memory 260 of lightweight node computing device 250 may also store dataand/or computer executable instructions used in performance of one ormore aspects described herein. For example, memory 260 may store digitalsignature information 261 and one or more hash functions 222 and networkcommands 225. In some arrangements, digital signature information 261,hash functions 222, and/or network commands 225 may comprise a wallet oflightweight node computing device 250. Each of hash functions 222 andnetwork commands 225 stored in memory 260 of lightweight node computingdevice 250 may be respectively similar and/or identical to hashfunctions 222 network commands 225 stored in memory 220 of full nodecomputing device 210.

In regard to the digital signature information, each of digitalsignature information 261 stored in memory 260 of lightweight nodecomputing device 250 and digital signature information 221 stored inmemory 220 of full node computing device 210 may comprise similar and/oridentical digital signature algorithms. However, the private/public keyinformation of digital signature information 261 stored in memory 260 oflightweight node computing device 250 may be different than that of theprivate/public key information of digital signature information 221stored in memory 220 of full node computing device 210. Furthermore, theprivate/public key information of each node, whether full orlightweight, in a decentralized P2P computing network may be unique tothat particular node. For example, a first node in a decentralized P2Pcomputing network may have first private/public key information, asecond node may have second private/public key information, a third nodemay have third private/public key information, and so on, wherein eachof the private/public key information is unique to the particular node.As such, the private/public key information may serve as a uniqueidentifier for the nodes in a decentralized P2P computing network.

Each of digital signature information 261, hash functions 222, andnetwork commands 225 may be used and/or executed by one or moreprocessors 251 of lightweight node computing device 250 to requestexecution of network functions in a decentralized P2P network. Forexample, in order to request execution of network functions, such asbalance sheet transactions and/or smart contract operations, processors251 of lightweight node computing device 250 may execute networkcommands 225 to broadcast the network function to a decentralized P2Pnetwork comprising a plurality of full nodes and/or lightweight nodes.The request may be digitally signed by lightweight node computing device250 with usage of the private/public key information and throughexecution of the digital signature algorithms of digital signatureinformation 261.

Furthermore, memory 260 of lightweight node computing device 250 maystore blockchain 226. Blockchain 226 stored in memory 260 of lightweightnode computing device 250 may include at least block 227 n, whereinblock 227 n represents the most immediate block of blockchain 226. Assuch, the blockchain 226, which may be a replica or copy of theblockchain of the decentralized P2P network in which lightweight nodecomputing device 250 operates, may be a partial or incomplete copy ofthe blockchain of the decentralized P2P network. In some instances,however, blockchain 226 may include a blocks 227A, 227B, 227C, . . . 227n, wherein block 227A represents the first block (e.g., genesis block)of blockchain 226 and block 227 n represents the most immediate block ofblockchain 226. As such, the blockchain 226 may be a full or completecopy of the blockchain of the decentralized P2P network. Each of theblocks within blockchain 226 may include information corresponding tothe one or more network functions executed by the decentralized P2Pnetwork.

Blockchain-Based Digital Token Utilization

FIG. 4 depicts an illustrative digital token utilization system that maybe used in accordance with one or more example embodiments describedherein. Digital token utilization system 400 may include a decentralizedP2P network 401, network nodes 403A-403N, networks 405A-405C, a serviceprovider computing device 407, a lender computing device 409, and aborrower computing device 411. Service provider computing device 407 maycommunicate with decentralized P2P network 401 through network 405A.Lender computing device 409 may communicate with decentralized P2Pnetwork 401 through network 405B. Borrower computing device 411 maycommunicate with decentralized P2P network 401 through network 405C.Digital token utilization system 400 may include additional and/or othercomputing devices and/or networks similar to decentralized P2P network401, network nodes 403A-403N, networks 405A-405C, service providercomputing device 407, lender computing device 409, and borrowercomputing device 411.

Decentralized P2P network 401 may be a public or private decentralizednetwork, and may be similar to decentralized P2P network 270 describedabove in connection with FIG. 2. Decentralized P2P network 401 mayinclude network nodes 403A-403N. A network node of network nodes403A-403N may be any type of computing device or computing platform. Anetwork node of network nodes 403A-403N may be configured to operate asa full node in decentralized P2P network 401. A network node of networknodes 403A-403N may be similar to full node computing devices 201A-201Fdescribed above in connection with FIG. 2, or full node computing device210 described above in connection with FIG. 3A. As such, a network nodeof network nodes 403A-403N may include (e.g., store in its memory) atleast a portion of a blockchain corresponding to decentralized P2Pnetwork 401.

The blockchain corresponding to decentralized P2P network 401 may storeinformation related to network functions (e.g., balance sheettransactions, data storage operations, smart contract operations, or thelike) of decentralized P2P network 401. Additionally or alternatively,the blockchain of decentralized P2P network 401 may store informationrelated to digital tokens, service provider tokens, credit tokens,and/or other types of tokens, as will be described in further detailbelow.

The digital tokens may include any type of digital token. The digitaltokens may be cryptocurrency and/or cryptocurrency digitally backed byfiat currency, gold, or other objects of value. The service providertoken may be a type of cryptocurrency and/or cryptocurrency digitallybacked by fiat currency, gold, or other objects of value. The serviceprovider token may be issued by service provider computing device 407 tofacilitate depositing and withdrawing of the digital tokens as furtherdiscussed below. The credit token may be a type of token that representsits holder's reputation (e.g., the holder's creditworthiness). Thecredit token may be issued by service provider computing device 407. Thecredit token may be configured to be freely transferrable or not freelytransferrable. The credit token may be used to facilitate lending thedigital tokens as further discussed below.

As a full node in decentralized P2P network 401, a network node ofnetwork nodes 403A-403N may be configured to executed requested networkfunctions, maintain inter-nodal agreement as to the state of theblockchain of decentralized P2P network 401, and request execution ofnetwork functions. Additionally or alternatively, a network node ofnetwork nodes 403A-403N may be configured to operate as a lightweightnode.

Each of service provider computing device 407, lender computing device409, and/or borrower computing device 411 may be configured to operateas a lightweight node communicating with decentralized P2P network 401.Each of service provider computing device 407, lender computing device409, and/or borrower computing device 411 may be similar to lightweightnode computing devices 250A-250B described above in connection with FIG.2, or lightweight node computing device 250 described above inconnection with FIG. 3B. As a lightweight node computing device, serviceprovider computing device 407, lender computing device 409, and/orborrower computing device 411 may each be configured to interface withdecentralized P2P network 401 by requesting execution of networkfunctions related to facilitating the blockchain-based digital tokenutilization processes described herein. Additionally or alternatively,service provider computing device 407, lender computing device 409,and/or borrower computing device 411 may be configured to operate as afull node.

Each of service provider computing device 407, lender computing device409, and/or borrower computing device 411 may be associated with aparticular entity, such as a company or an enterprise organization. Forexample, service provider computing device 407 may be associated with aservice provider, lender computing device 409 may be associated with alender, and borrower computing device 411 may be associated with aborrower. The service provider may accept deposits of the digital tokensfrom the lender, and provide loans of the digital tokens to theborrower. Service provider computing device 407, lender computing device409, and/or borrower computing device 411 may each be configured tointerface with its associated entity via a user interface, a webinterface, a computing device, or the like.

Each of service provider computing device 407, lender computing device409, and/or borrower computing device 411 may have a digital tokenwallet stored in its memory which may be associated with a digitaltoken. The digital token wallet may be associated with a public key,which may serve to identify the digital token wallet. The digital tokenwallet may be associated with a private key, which may be used todigitally sign requests and/or operations related to the digital tokenwallet in order to verify the authenticity of the requests and/oroperations.

Each of service provider computing device 407 and/or lender computingdevice 409 may have a service provider token wallet stored in its memorywhich may be associated with the service provider token. Similar to thedigital token wallets, the service provider token wallets may beassociated with public keys and private keys. Each of service providercomputing device 407 and/or borrower computing device 411 may have acredit token wallet stored in its memory which may be associated withthe credit token. The credit token wallets may be associated with publickeys and private keys. Additionally or alternatively, service providercomputing device 407, lender computing device 409, and/or borrowercomputing device 411 may each have any other type of wallet associatedwith other types of tokens.

FIGS. 5A-5H depict an illustrative event sequence for digital tokenutilization in accordance with one or more example embodiments describedherein. While the steps of the event sequence are described in aparticular order, the steps may be performed in any order withoutdeparting from the scope of the disclosure provided herein. Although theevent sequence is described as being performed by a particulararrangement of computing systems, devices, and networks (e.g., serviceprovider computing device 407, lender computing device 409, borrowercomputing device 411, and network nodes 403A-403N in decentralized P2Pnetwork 401), the processes may be performed by a greater or smallernumber of computing systems, devices, and/or networks, and/or by anytype of computing system, device, and/or network.

Referring to FIG. 5A, in step 501, service provider computing device 407may receive a digital token collection request. The digital tokencollection request may be received via an application operating locallyon the service provider computing device 407. For example, a serviceprovider associated with service provider computing device 407 mayenter, via a user interface of the application, the digital tokencollection request. Additionally or alternatively, the digital tokencollection request may be received through a web interface associatedwith service provider computing device 407.

The digital token collection request may indicate that service providercomputing device 407 intends to accept deposits of digital tokens. Thedigital token collection request may indicate a type of digital token,an appreciation rate associated with the digital token, an exchange ratebetween the digital token and the service provider token, and walletinformation (e.g., public keys) associated with service providercomputing device 407.

In step 502, service provider computing device 407 may generate acollection smart contract based on the digital token collection request.The collection smart contract may include one or more algorithms and/orcomputer executable functions that control the collecting and returningof digital tokens (e.g., in exchange of the service provider token). Thecollection smart contract may be configured to create a number of datafields, which may store values for an amount of digital tokens of aparticular type (a digital token quantity data field), an amount of theservice provider tokens (a service provider token quantity data field),an exchange rate between the digital token and the service providertoken (an exchange rate data field), and/or an appreciation rateassociated with the digital token (an appreciation rate data field).

In step 503, service provider computing device 407 may deploy thecollection smart contract to the blockchain of decentralized P2P network401. Service provider computing device 407 may compile the collectionsmart contract, and send, to decentralized P2P network 401, a networkfunction request including the collection smart contract. The networkfunction request may be broadcasted to network nodes 403A-403N. In someexamples, the broadcasting of the network function request may beperformed by each of the full node computing devices (e.g., networknodes 403A-403N) comprising decentralized P2P network 401 so that eachof the full node computing devices receives the network functionrequest.

In step 504, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.

The generated block added to the blockchain of decentralized P2P network401 may include the collection smart contract generated by serviceprovider computing device 407. The operations of generating and addingthe block to the blockchain may be similar to those described above inconnection with FIG. 2.

In step 505, a public key corresponding to the collection smart contractstored in the blockchain of decentralized P2P network 401 may bereturned by one or more of network nodes 403A-403N to service providercomputing device 407. For example, the public key may be returnedresponsive to storing the collection smart contract on the blockchain ofdecentralized P2P network 401. The public key may uniquely identify thecollection smart contract in the blockchain of decentralized P2P network401.

Referring to FIG. 5B, in step 506, service provider computing device 407may send a token collection configuration request to network nodes403A-403N in decentralized P2P network 401. The token collectionconfiguration request may be a smart contract operation request, and mayinclude the public key corresponding to the collection smart contract inthe blockchain of decentralized P2P network 401.

The token collection configuration request may request to transfer anamount of digital tokens of a particular type from the digital tokenwallet associated with service provider computing device 407 to thecollection smart contract. The request to transfer the digital token maybe digitally signed by the private key of the digital token walletassociated with service provider computing device 407. Additionally oralternatively, the token collection configuration request may request totransfer an amount of the service provider tokens from the serviceprovider token wallet associated with service provider computing device407 to the collection smart contract. The request to transfer theservice provider token may be digitally signed by the private key of theservice provider token wallet associated with service provider computingdevice 407. The token collection configuration request may request topopulate the exchange rate data field and/or the appreciation rate datafield in the collection smart contract with the corresponding valuesspecified in the digital token collection request.

In step 507, network nodes 403A-403N of decentralized P2P network 401may receive the token collection configuration request (e.g., fromservice provider computing device 407), and may execute the collectionsmart contract (e.g., by applying the token collection configurationrequest to the collection smart contract).

For example, each of network nodes 403A-403N may identify, within theblockchain of decentralized P2P network 401, the block comprising thecollection smart contract based on the public key corresponding to thecollection smart contract. After verifying that the digital signaturesassociated with the token collection configuration request are valid,each of network nodes 403A-403N may transfer the digital token and/orthe service provider token from the wallets associated with serviceprovider computing device 407 to the collection smart contract. Forexample, each of network nodes 403A-403N may decrease the value of thedigital token wallet associated with service provider computing device407 by the amount specified in the token collection configurationrequest, and increase the value of the digital token quantity data fieldin the collection smart contract by the same amount. The digital tokensand/or service provider tokens may remain in the collection smartcontract until further network function requests are received.Additionally or alternatively, based on the token collectionconfiguration request, each of network nodes 403A-403N may set thevalues of the exchange rate data field and the appreciation rate datafield in the collection smart contract.

In step 508, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the token collection configuration request generated byservice provider computing device 407. Additionally or alternatively,the generated block may include the most recent state of the blockchainof decentralized P2P network 401 (e.g., values of wallets, values ofdata fields in smart contracts, or the like) after applying the tokencollection configuration request to the collection smart contract.

In step 509, lender computing device 409 may send a lender input requestto network nodes 403A-403N in decentralized P2P network 401. The lenderinput request may be a smart contract operation request, and may includethe public key corresponding to the collection smart contract in theblockchain of decentralized P2P network 401.

The lender input request may request to transfer digital tokens of aparticular type from the digital token wallet associated with lendercomputing device 409 to the collection smart contract. The lender inputrequest may indicate that lender computing device 409 intends to depositan amount of the digital tokens for an appreciation rate. The lenderinput request may specify the quantity of the digital tokens that lendercomputing device 409 intends to transfer. The lender input request maybe digitally signed by a private key of the digital token walletassociated with lender computing device 409.

In step 510, network nodes 403A-403N of decentralized P2P network 401may receive the lender input request (e.g., from lender computing device409), and may execute the collection smart contract (e.g., by applyingthe lender input request to the collection smart contract). For example,each of network nodes 403A-403N may identify, within the blockchain ofdecentralized P2P network 401, the block comprising the collection smartcontract based on the public key corresponding to the collection smartcontract. After verifying that the digital signature associated with thelender input request is valid, each of network nodes 403A-403N maytransfer the specified amount of the digital tokens from the digitaltoken wallet associated with lender computing device 409 to thecollection smart contract. For example, each of network nodes 403A-403Nmay decrease the value of the digital token wallet associated withlender computing device 409 by the specified amount, and may increasethe value of the digital token quantity data field in the collectionsmart contract by the specified amount.

Referring to FIG. 5C, in step 511, execution of the collection smartcontract may cause network nodes 403A-403N to transmit the digitaltokens to the digital token wallet associated with service providercomputing device 407. For example, service provider computing device 407may have a digital token wallet stored in its memory which may beassociated with the digital token, and execution of the collection smartcontract may cause network nodes 403A-403N to transmit the digitaltokens to service provider computing device 407.

The amount of the digital tokens to be transmitted to the digital tokenwallet associated with service provider computing device 407 may be allor a portion of the digital tokens received from the digital tokenwallet associated with lender computing device 409. For example, aportion of the digital tokens received from the digital token walletassociated with lender computing device 409 may remain in the collectionsmart contract as anytime available digital tokens for lender computingdevice 409 to withdraw in step 514. The portion remaining in thecollection smart contract may be calculated based on historicalwithdrawal events. Additionally or alternatively, a portion of thedigital tokens received from the digital token wallet associated withlender computing device 409 may be transferred to a distribution smartcontract configured to facilitate lending digital tokens to borrowercomputing device 411 as discussed below.

In step 512, execution of the collection smart contract may causenetwork nodes 403A-403N to transmit the service provider tokens to theservice provider token wallet associated with lender computing device409. For example, lender computing device 409 may have a serviceprovider token wallet stored in its memory which may be associated withthe service provider token, and execution of the collection smartcontract may cause network nodes 403A-403N to transmit the serviceprovider tokens to lender computing device 409.

The amount of the service provider tokens to be transmitted to theservice provider token wallet associated with lender computing device409 may be determined based on the amount of the digital tokens receivedfrom the digital token wallet associated with lender computing device409 and the exchange rate between the digital token and the serviceprovider token. For example, if the exchange rate between the digitaltoken and the service provider token is R:1, the amount of the serviceprovider tokens to be transmitted to the service provider token walletassociated with lender computing device 409 may be the amount of thedigital tokens received from the digital token wallet associated withlender computing device 409 divided by R. Different types of digitaltokens may have same or different exchange rates to the service providertoken.

The service provider token may be used to facilitate the deposit andwithdrawal of the digital token. The service provider token may beissued by service provider computing device 407. For example, theservice provider token may be issued according to a particular technicalstandard, such as the ERC20 technical standard. Additionally oralternatively, the service provider token may be backed by physicalobjects of value, which may be audited by a third party.

In step 513, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the lender input request generated by lender computingdevice 409. Additionally or alternatively, the generated block mayinclude the most recent state of the blockchain of decentralized P2Pnetwork 401 (e.g., values of wallets, values of data fields in smartcontracts, or the like) after applying the lender input request to thecollection smart contract.

In step 514, lender computing device 409 may send a lender outputrequest to network nodes 403A-403N in decentralized P2P network 401. Thelender output request may be a smart contract operation request, and mayinclude the public key corresponding to the collection smart contract inthe blockchain of decentralized P2P network 401.

The lender output request may request to transfer an amount of theservice provider tokens from the service provider token walletassociated with lender computing device 409 to the collection smartcontract. The lender output request may indicate that lender computingdevice 409 intends to withdraw an amount of digital tokens of aparticular type based on the returned service provider tokens. Thelender output request may specify the amount of the service providertokens that lender computing device 409 intends to transfer. The lenderoutput request may be signed by a private key of the service providertoken wallet associated with lender computing device 409.

In step 515, network nodes 403A-403N of decentralized P2P network 401may receive the lender output request (e.g., from lender computingdevice 409), and may execute the collection smart contract (e.g., byapplying the lender output request to the collection smart contract), ina similar manner as in step 510.

For example, each of network nodes 403A-403N may identify, within theblockchain of decentralized P2P network 401, the block comprising thecollection smart contract based on the public key corresponding to thecollection smart contract. After verifying that the digital signatureassociated with the lender output request is valid, each of networknodes 403A-403N may transfer the specified amount of the serviceprovider tokens from the service provider token wallet associated withlender computing device 409 to the collection smart contract. Forexample, each of network nodes 403A-403N may decrease the value of theservice provider token wallet associated with lender computing device409 by the amount specified in the lender output request, and mayincrease the value of the service provider token quantity data field inthe collection smart contract by the specified amount.

Referring to FIG. 5D, in step 516, execution of the collection smartcontract may cause network nodes 403A-403N to transmit the digitaltokens to the digital token wallet associated with lender computingdevice 409. For example, lender computing device 409 may have a digitaltoken wallet stored in its memory which may be associated with thedigital token, and execution of the collection smart contract may causenetwork nodes 403A-403N to transmit the digital tokens to lendercomputing device 409.

The amount of the digital tokens to be transmitted to the digital tokenwallet associated with lender computing device 409 may be determinedbased on the amount of the service provider tokens received from theservice provider token wallet associated with lender computing device409 and an updated exchange rate between the digital token and theservice provider token.

The exchange rate between the digital token and the service providertoken may be updated based on the appreciation rate associated with thedigital token. The appreciation rate may be a rate per second, a rateper minute, a rate per hour, a rate per day, or the like. Execution ofthe collection smart contract may cause network nodes 403A-403N todetermine a time period between receiving the lender input request andreceiving the lender output request (e.g., based on timestamps recordedat the time of receiving the requests). The network nodes 403A-403N maycalculate an overall appreciation rate for the determined time periodbased on the appreciation rate and the time period (e.g., through thesimple interest calculation method, the compound interest calculationmethod, or the like). The updated exchange rate may be equal to theprevious exchange rate multiplied by the overall appreciation rate forthe determined time period.

Additionally or alternatively, the network nodes 403A-403N mayperiodically update the exchange rate (e.g., every hour, every day, orthe like). Additionally or alternatively, the network nodes 403A-403Nmay update the exchange rate every time the collection smart contract isexecuted. In such arrangements, the exchange rate between the digitaltoken and the service provider token may be constantly increasing,representing the appreciation value of the deposited digital tokens. Forexample, when lender computing device 409 deposits the digital tokens tothe collection smart contract, the exchange rate between the digitaltoken and the service provider token may be 101:100. When lendercomputing device 409 withdraws the digital tokens from the collectionsmart contract, the exchange rate between the digital token and theservice provider token may be 101.05:100 (increased based on theappreciation rate associated with the digital token). Lender computingdevice 409 may withdraw its deposited digital tokens together withinterest based on simply transmitting the service provider tokens to thecollection smart contract.

In step 517, execution of the collection smart contract may causenetwork nodes 403A-403N to transmit the service provider tokens to theservice provider token wallet associated with service provider computingdevice 407. For example, service provider computing device 407 may havea service provider token wallet stored in its memory which may beassociated with the service provider token, and execution of thecollection smart contract may cause network nodes 403A-403N to transmitthe service provider tokens to service provider computing device 407.

The amount of the service provider tokens to be transmitted to theservice provider token wallet associated with service provider computingdevice 407 may be all or a portion of the service provider tokensreceived from the service provider token wallet associated with lendercomputing device 409. For example, a portion of the service providertokens received from the service provider token wallet associated withlender computing device 409 may remain in the collection smart contractfor future use. The portion remaining in the collection smart contractmay be determined based on historical deposit events.

In step 518, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the lender output request generated by lender computingdevice 409. Additionally or alternatively, the generated block mayinclude the most recent state of the blockchain of decentralized P2Pnetwork 401 (e.g., values of wallets, values of data fields in smartcontracts, or the like) after applying the lender output request to thecollection smart contract.

In step 519, service provider computing device 407 may receive a digitaltoken distribution request. The digital token distribution request maybe received via an application operating locally on the service providercomputing device 407. For example, a service provider associated withservice provider computing device 407 may enter, via a user interface ofthe application, the digital token distribution request. Additionally oralternatively, the digital token distribution request may be receivedthrough a web interface associated with service provider computingdevice 407.

The digital token distribution request may indicate that serviceprovider computing device 407 intends to provide loans of digital tokensof a particular type. The digital token distribution request mayindicate a type of digital token, an interest rate associated with thedigital token, conditions for allocating an amount of the digital tokensto borrower computing device 411 (e.g., an exchange rate between thedigital token and a credit token), and wallet information (e.g., publickeys) associated with service provider computing device 407.

For different types of digital tokens, same or different interest ratesmay be used. The interest rates associated with the different types ofdigital tokens may be determined based on the risk levels associatedwith the different digital tokens, the market values of the differentdigital tokens, or the like. Additionally or alternatively, the interestrate associated with a type of digital token may be determined based onthe appreciation rate, associated with the digital token, which is usedin the collection smart contract. For example, the interest rateassociated with the digital token may be set to be higher than theappreciation rate associated with the digital token.

In step 520, service provider computing device 407 may generate adistribution smart contract based on the digital token distributionrequest. The distribution smart contract may include one or morealgorithms and/or computer executable functions that control thedistributing and recollecting of the digital tokens.

The distribution smart contract may be configured to create a number ofdata fields, which may store values for an amount of digital tokens of aparticular type (a digital token quantity data field), quantities ofother types of tokens (token quantity data fields), exchange ratesbetween the digital token and the other types of tokens (exchange ratedata fields), and/or an interest rate associated with the digital token(interest rate data field).

The distribution smart contract may include programmatic conditions forallocating the digital tokens to borrower computing device 411. Forexample, borrower computing device 411 may transmit another type oftoken (e.g., the credit token) to the distribution smart contract ascollateral, and the distribution smart contract may use an exchange ratebetween the digital token and the other type of token to calculatewhether and/or how much digital tokens may be distributed to borrowercomputing device 411. Additionally or alternatively, the distributionsmart contract may allow borrower computing device 411 to get an amountof the digital tokens even if the distribution smart contract does notreceive any tokens as collateral. After receiving, from borrowercomputing device 411, a request to obtain an amount of the digitaltokens, the distribution smart contract may request authorization fromservice provider computing device 407 before sending the requesteddigital tokens to borrower computing device 411. Service providercomputing device 407 may assess whether to authorize sending the digitaltokens to borrower computing device 411 based on various factors, suchas a credit score associated with borrower computing device 411.

Referring to FIG. 5E, in step 521, service provider computing device 407may deploy the distribution smart contract to the blockchain ofdecentralized P2P network 401. Service provider computing device 407 maycompile the distribution smart contract, and send, to decentralized P2Pnetwork 401, a network function request including the distribution smartcontract. The network function request may be broadcasted to networknodes 403A-403N. In some examples, the broadcasting of the networkfunction request may be performed by each of the full node computingdevices (e.g., network nodes 403A-403N) comprising decentralized P2Pnetwork 401 so that each of the full node computing devices receives thenetwork function request.

In step 522, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2. Thegenerated block added to the blockchain of decentralized P2P network 401may include the distribution smart contract generated by serviceprovider computing device 407.

In step 523, a public key corresponding to the distribution smartcontract in the blockchain of decentralized P2P network 401 may bereturned by one or more of network nodes 403A-403N to service providercomputing device 407. For example, the public key may be returnedresponsive to storing the distribution smart contract on the blockchainof decentralized P2P network 401. The public key may uniquely identifythe distribution smart contract in the blockchain of decentralized P2Pnetwork 401.

In step 524, service provider computing device 407 may send a tokendistribution configuration request to network nodes 403A-403N indecentralized P2P network 401. The token distribution configurationrequest may be a smart contract operation request, and may include thepublic key corresponding to the distribution smart contract in theblockchain of decentralized P2P network 401.

The token distribution configuration request may request to transfer anamount of the digital tokens from the digital token wallet associatedwith service provider computing device 407 to the distribution smartcontract. The transfer request may be signed by a private key of thedigital token wallet associated with service provider computing device407. The token distribution configuration request may request topopulate the exchange rate data fields and/or the interest rate datafield in the distribution smart contract with values specified in thedigital token distribution request.

In step 525, the network nodes 403A-403N of decentralized P2P network401 may receive the token distribution configuration request (e.g., fromservice provider computing device 407), and may executed thedistribution smart contract (e.g., by applying the token distributionconfiguration request to the distribution smart contract).

For example, each of network nodes 403A-403N may identify, within theblockchain of decentralized P2P network 401, the block comprising thedistribution smart contract based on the public key corresponding to thedistribution smart contract. After verifying that the digital signatureassociated with the token distribution configuration request is valid,each of network nodes 403A-403N may transfer the digital tokens from thedigital token wallet associated with service provider computing device407 to the distribution smart contract. For example, each of the networknodes 403A-403N may decrease the value of the digital token walletassociated with service provider computing device 407 by an amount(e.g., specified in the token distribution configuration request), andincrease the value of the digital token quantity data field in thedistribution smart contract by the same amount. The digital tokens mayremain in the distribution smart contract until further network functionrequests are received. Additionally or alternatively, based on the tokendistribution configuration request, each of network nodes 403A-403N mayset the values of the exchange rate data fields and/or the interest ratedata field in the distribution smart contract.

Referring to FIG. 5F, in step 526, at least one of network nodes403A-403N in decentralized P2P network 401 may generate a blockcorresponding to the blockchain of decentralized P2P network 401, andmay add the block to the blockchain. For example, the network node ofnetwork nodes 403A-403N that generates the block may broadcast the blockto other network nodes of network nodes 403A-403N. The other networknodes of network nodes 403A-403N may validate the block, and add theblock to their copies of the blockchain. The operations of generatingand adding the block to the blockchain may be similar to those describedabove in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the token distribution configuration request generatedby service provider computing device 407. Additionally or alternatively,the generated block may include the most recent state of the blockchainof decentralized P2P network 401 (e.g., values of wallets, values ofdata fields in smart contracts, or the like) after applying the tokendistribution configuration request to the distribution smart contract.

In step 527, borrower computing device 411 may send a borrower outputrequest to network nodes 403A-403N in decentralized P2P network 401. Theborrower output request may be a smart contract operation request, andmay include the public key corresponding to the distribution smartcontract in the blockchain of decentralized P2P network 401.

The borrower output request may request to transfer an amount of thedigital tokens from the distribution smart contract to the digital tokenwallet associated with borrower computing device 411. The borroweroutput request may indicate that borrower computing device 411 intendsto obtain an amount of the digital tokens at an interest rate.

Additionally or alternatively, the borrower output request may requestto transfer other types of tokens as collateral from wallets associatedwith borrower computing device 411 to the distribution smart contract.The other types of tokens may include, for example, a credit token ordigital tokens of types other than the type that borrower computingdevice 411 intends to obtain. The other types of tokens may be backed bygold, real property, personal property, intellectual property, or thelike, which may be audited by a third party.

The credit token may be issued by service provider computing device 407.The credit token may be configured to be freely transferrable or notfreely transferrable. When borrower computing device 411 begins toparticipate in decentralized P2P network 401, service provider computingdevice 407 may issue an initial amount of the credit tokens to borrowercomputing device 411. The initial amount of the credit tokens may bedetermined based on a credit score associated with borrower computingdevice 411. The credit score may be determined based on, for example,data obtained from government agencies, insurance companies,telecommunication providers, utility providers, or the like.

Additionally or alternatively, the credit token may be issued toborrower computing device 411 based on historical event data associatedwith borrower computing device 411. As discussed in more details below,if borrower computing device 411 returns its obtained digital tokenswith additional digital tokens as interest and within a thresholdperiod, an amount of the credit tokens may be issued to borrowercomputing device 411 as a reward and as an indication of the increasingcreditworthiness of borrower computing device 411.

In step 528, network nodes 403A-403N of decentralized P2P network 401may receive the borrower output request (e.g., from borrower computingdevice 411), and may execute the distribution smart contract (e.g., byapplying the borrower output request to the distribution smartcontract).

For example, each of network nodes 403A-403N may identify, within theblockchain of decentralized P2P network 401, the block comprising thedistribution smart contract based on the public key corresponding to thedistribution smart contract. After verifying that the digitalsignature(s) associated with the borrower output request is valid, eachof network nodes 403A-403N may transfer, from the credit token walletassociated with borrower computing device 411 to the distribution smartcontract, an amount of credit tokens (e.g., specified in the borroweroutput request). For example, each of network nodes 403A-403N maydecrease the value of the credit token wallet associated with borrowercomputing device 411 by the specified amount, and may increase the valueof a credit token quantity data field in the distribution smart contractby the specified amount. The credit tokens may remain in thedistribution smart contract. Additionally or alternatively, execution ofthe distribution smart contract may cause other types of tokens to betransferred from wallets associated with borrower computing device 411to the distribution smart contract.

In step 529, execution of the distribution smart contract may causenetwork nodes 403A-403N to transmit the digital tokens to the digitaltoken wallet associated with borrower computing device 411. For example,borrower computing device 411 may have a digital token wallet stored inits memory which may be associated with the digital token, and executionof the collection smart contract may cause network nodes 403A-403N totransmit the digital tokens to borrower computing device 411.

The amount of the digital tokens to be transmitted to the digital tokenwallet associated with borrower computing device 411 may be determinedbased on the other types of tokens received from the borrower computingdevice 411. For example, the amount of the digital tokens to betransmitted may be determined based on an exchange rate between thedigital token and the credit token.

In step 530, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the borrower output request generated by borrowercomputing device 411. Additionally or alternatively, the generated blockmay include the most recent state of the blockchain of decentralized P2Pnetwork 401 (e.g., values of wallets, values of data fields in smartcontracts, or the like) after applying the borrower output request tothe distribution smart contract.

Referring to FIG. 5G, in step 531, borrower computing device 411 maysend a borrower input request to network nodes 403A-403N indecentralized P2P network 401. The borrower input request may be a smartcontract operation request, and may include the public key correspondingto the distribution smart contract in the blockchain of decentralizedP2P network 401.

The borrower input request may request to transfer the obtained digitaltokens plus an additional amount of the digital tokens representinginterest from the digital token wallet associated with borrowercomputing device 411 to the distribution smart contract. The borrowerinput request may indicate that borrower computing device 411 intends toreturn the obtained digital tokens. The borrower input request may besigned by a private key of the digital token wallet associated withborrower computing device 411.

In step 532, network nodes 403A-403N of decentralized P2P network 401may receive the borrower input request (e.g., from borrower computingdevice 411), and may execute the distribution smart contract (e.g., byapplying the borrower input request to the distribution smart contract).

For example, each of network nodes 403A-403N may identify, within theblockchain of decentralized P2P network 401, the block comprising thedistribution smart contract based on the public key corresponding to thedistribution smart contract. After verifying that the digital signatureassociated with the borrower input request is valid, each of networknodes 403A-403N may transfer the specified amount of the digital tokensfrom the digital token wallet associated with borrower computing device411 to the distribution smart contract. For example, each of networknodes 403A-403N may decrease the value of the digital token walletassociated with borrower computing device 411 by the specified amount,and may increase the value of the digital token quantity data field inthe distribution smart contract by the specified amount.

In step 533, execution of the collection smart contract may causenetwork nodes 403A-403N to transmit the tokens representing collateral(e.g., the credit tokens) to the wallets associated with borrowercomputing device 411. For example, borrower computing device 411 mayhave wallets stored in its memory which may be associated with thecollateral token, and execution of the collection smart contract maycause network nodes 403A-403N to transmit the collateral tokens toborrower computing device 411.

Network nodes 403A-403N may return the collateral tokens previouslyreceived from the wallets associated with borrower computing device 411.Additionally or alternatively, responsive to determining that borrowercomputing device 411 has returned the borrowed digital tokens within aparticular time threshold, network nodes 403A-403N may transmit anadditional amount of credit tokens to wallets associated with borrowercomputing device 411 as a reward. This additional amount of credittokens can be used to implement a reputation based lending system.

In step 534, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the borrower input request generated by borrowercomputing device 411. Additionally or alternatively, the generated blockmay include the most recent state of the blockchain of decentralized P2Pnetwork 401 (e.g., values of wallets, values of data fields in smartcontracts, or the like) after applying the borrower input request to thedistribution smart contract.

In step 535, as an additional or alternative step to step 533, networknodes 403A-403N may determine that borrower computing device 411 failsto properly return its obtained digital tokens with an additional amountof the digital tokens representing interest on time. Network nodes403A-403N may record the time when borrower computing device 411obtained the digital tokens (e.g., in step 527), and may set a timethreshold within which borrower computing device 411 is to return theobtained digital tokens together with an additional amount of thedigital tokens representing interest. The additional amount of thedigital tokens may be determined based on the value of the interest ratedata field in the distribution smart contract and the set timethreshold. Execution of the distribution smart contract may causenetwork nodes 403A-403N to determine whether the correct amount of thedigital tokens are returned by borrower computing device 411. If theanswer to this question is no, network nodes 403A-403N may proceed tostep 536.

Additionally or alternatively, network nodes 403A-403N may periodicallydetermine whether the time threshold has been reached since borrowercomputing device 411 obtained the digital tokens. If network nodes403A-403N determines that the time threshold has been reached andborrower computing device 411 has not returned the digital tokens,network nodes 403A-403N may proceed to step 536.

In step 536, execution of the distribution smart contract may causenetwork nodes 403A-403N to transmit the credit tokens (that may havebeen received from borrower computing device 411) to a credit tokenwallet associated with service provider computing device 407. Forexample, service provider computing device 407 may have a credit tokenwallet stored in its memory which may be associated with the credittoken, and execution of the distribution smart contract may causenetwork nodes 403A-403N to transmit the credit tokens to serviceprovider computing device 407. Additionally or alternatively, executionof the distribution smart contract may cause network nodes 403A-403N toforfeit or destroy all or a portion of the credit tokens. Additionallyor alternatively, the other types of tokens that were received ascollateral from borrower computing device 411 in step 527 may besimilarly transmitted to service provider computing device 407.

In step 537, at least one of network nodes 403A-403N in decentralizedP2P network 401 may generate a block corresponding to the blockchain ofdecentralized P2P network 401, and may add the block to the blockchain.For example, the network node of network nodes 403A-403N that generatesthe block may broadcast the block to other network nodes of networknodes 403A-403N. The other network nodes of network nodes 403A-403N mayvalidate the block, and add the block to their copies of the blockchain.The operations of generating and adding the block to the blockchain maybe similar to those described above in connection with FIG. 2.

The generated block added to the blockchain of decentralized P2P network401 may include the determination that borrower computing device 411failed to properly return its obtained digital tokens on time.Additionally or alternatively, the generated block may include the mostrecent state of the blockchain of decentralized P2P network 401 (e.g.,values of wallets, values of data fields in smart contracts, or thelike) after transmitting the collateral tokens to service providercomputing device 407.

FIG. 6 depicts an illustrative method for digital token utilization inaccordance with one or more example embodiments described herein. Instep 601, a computing platform configured to operate in a decentralizedP2P network and including one or more processors and memory storing atleast a portion of a blockchain of the decentralized P2P network mayregister, to the blockchain of the decentralized P2P network, acollection smart contract configured to facilitate collecting andreturning of digital tokens of a particular type. In step 603, thecomputing platform may send the digital tokens from a digital tokenwallet associated with a second computing device to the collection smartcontract. In step 603, the computing platform may send the digitaltokens with an amount of appreciation value from the collection smartcontract to the digital token wallet associated with the secondcomputing device. In step 607, the computing platform may register, tothe blockchain of the decentralized P2P network, a distribution smartcontract configured to facilitate distributing and recollecting thedigital tokens. In step 609, the computing platform may send other typesof tokens from wallets associated with a third computing device to thedistribution smart contract, and may send a corresponding amount of thedigital tokens from the distribution smart contract to a digital tokenwallet associated with the third computing device. In step 611, thecomputing platform may determine whether the third computing device hasreturned the digital tokens with an additional amount of the digitaltokens representing interest within a time threshold. If the computingplatform determines that the third computing device has returned thedigital tokens with the additional amount of the digital tokensrepresenting the interest within the time threshold, then the computingplatform may in step 615 return the other types of tokens from thedistribution smart contract to the wallets associated with the thirdcomputing device. If the computing platform determines that the thirdcomputing device has not returned the digital tokens with the additionalamount of the digital tokens representing the interest within the timethreshold, then the computing platform may in step 613 forfeit the othertypes of tokens in the distribution smart contract.

The example embodiments discussed herein may be used for depositing andlending of digital tokens. Lenders may deposit their digital tokens tothe example systems discussed herein, and borrowers may borrow thedigital tokens. Service provider tokens may be used to facilitate thedepositing of the digital tokens, and the credit tokens may be used tofacilitate the lending of the digital tokens. Using the service providertokens and the credit tokens, the depositing and lending processes maybe simplified. Additionally, the example systems discussed herein mayprovide a secure environment for depositing and lending tokens. Ascentralized computing systems may create a single point of failure, thedecentralized P2P network may facilitate depositing and lending tokenswith enhanced security.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A system, comprising: a data storage devicestoring at least a portion of a blockchain of a decentralized person toperson (P2P) network; a computing device comprising: one or moreprocessors; and memory storing computer readable instructions that, whenexecuted by the one or more processors, cause the computing device to:register, based on a first registration request, a collection smartcontract by adding a first new block to the blockchain, wherein thefirst new block comprises the collection smart contract; receive, from afirst user computing device, a first event message comprisinginformation corresponding to a first plurality of tokens, a smartcontract identifier, and a first device identifier associated with thefirst user computing device; authenticate the first event message basedon the first device identifier; execute, based on authentication of thefirst event message, the collection smart contract by causing transfer,by a service provider token holder to memory associated with thecollection smart contract, a first amount of service provider tokens;receive, from a second user computing device, a second event messagecomprising information corresponding to a second plurality of digitaltokens, the smart contract identifier, and a second device identifierassociated with the second user computing device; authenticate thesecond event message based on the second device identifier; and executethe collection smart contract based on an authentication of the secondevent message, by causing transfer from a digital token holderassociated with the second user computing device and to memoryassociated with the collection smart contract, a first amount of thedigital tokens; and transfer, from the memory associated with thecollection smart contract to a service provider token holder associatedwith the second user computing device, the second amount of the serviceprovider tokens based on a token exchange rate.
 2. The system of claim1, wherein the computer readable instructions, when executed by the oneor more processors, further cause the computing device to: receive, fromthe second user computing device, a third event message comprising anidentifier of the collection smart contract; and transfer, based onvalidation of the third event message and from the service providertoken holder associated with the second user computing device to amemory associated with the collection smart contract, a third amount ofthe service provider tokens; determine, based on a digital tokenappreciation rate and a duration between receiving the second eventmessage and receiving the third event message, an updated digital tokenexchange rate; transfer, from the memory associated with the collectionsmart contract and to the digital token holder associated with thesecond user computing device, a second amount of the digital tokenscorresponding to the third amount of the service provider tokens and theupdated digital token exchange rate.
 3. The system of claim 1, whereinthe computer readable instructions, when executed by the one or moreprocessors, further cause the computing device to: receive, from thefirst user computing device, a second registration request forregistering a distribution smart contract; register the distributionsmart contract to the blockchain as a second new block associated withthe distribution smart contract; execute, based on an authenticatedfourth event message, the distribution smart contract, by causingtransfer a third amount of digital tokens from a digital token holderassociated with the first user computing device and to a memoryassociated with the distribution smart contract; receive, from a thirduser computing device, a fifth event message indicating a first amountof credit tokens and an identifier of the distribution smart contract;and based on an authenticated fifth event message received from a thirduser computing device: transfer, from a credit token holder associatedwith the third user computing device and to the memory associated withthe distribution smart contract, a first amount of the credit tokens;determine, based on the first amount of the credit tokens and anexchange rate between the digital tokens and the credit tokens, a fourthamount of the digital tokens; and transfer, based on the first amount ofcredit tokens and an credit token exchange rate, a fourth amount of thedigital tokens from the distribution smart contract and to a digitaltoken holder associated with the third user computing device.
 4. Thesystem of claim 3, wherein the computer readable instructions, whenexecuted by the one or more processors, further cause the computingdevice to: based on an authenticated sixth event message received fromthe third computing device: transfer, based on an interest rateassociated with the digital tokens, a fifth amount of the digital tokensfrom the digital token holder associated with the third user computingdevice and to the memory associated with distribution smart contract. 5.The system of claim 4, wherein the computer readable instructions, whenexecuted by the one or more processors, further cause the computingdevice to: based on a determination that the fifth amount of the digitaltokens does not correspond to an expected amount of the digital tokens,transfer, from the distribution smart contract and to a memoryassociated with a credit token holder associated with the first usercomputing device, the first amount of the credit tokens.
 6. The systemof claim 3, wherein the computer readable instructions, when executed bythe one or more processors, further cause the computing device to:transfer, from the collection smart contract and to the distributionsmart contract, a portion of the first amount of the digital tokensbased on an authentication of the second event message.
 7. The system ofclaim 3, wherein the computer readable instructions, when executed bythe one or more processors, further cause the computing device to:determine, based on a credit score associated with the third usercomputing device, a second amount of the credit tokens; and assign thesecond amount of the credit tokens to the credit token holder associatedwith the third user computing device.
 8. A method for managing, in adecentralized peer-to-peer (P2P) network, a blockchain of thedecentralized P2P network: registering, based on a first registrationrequest from a first user computing device, a collection smart contractby adding a first new block to the blockchain, wherein the first newblock comprises the collection smart contract; authenticating a firstevent message based on a digital signature associated with the firstuser computing device, wherein the first event message is received fromthe first user computing device and comprises an indication of a firstamount of service provider tokens; transferring, from a service providertoken holder associated with the first user computing device and to amemory associated with the collection smart contract, the first amountof the service provider tokens; authenticating a second event messagereceived from a second user computing device based on a second digitalsignature associated with the second user computing device; and based onthe second event message: transferring, from a digital token holderassociated with the second user computing device and to the memoryassociated with the collection smart contract, a first amount of thedigital tokens; and transferring, based on a digital token exchange rateand from the memory associated with the collection smart contract and toa service provider token holder associated with the second usercomputing device, a second amount of the service provider tokens.
 9. Themethod of claim 8, further comprising: based on a third event messagereceived from the second computing device: transferring, from theservice provider token holder associated with the second user computingdevice and to the memory associated with the collection smart contract,a third amount of the service provider tokens; determining an updatedexchange rate between the digital tokens and the service providertokens; and transferring, based on the updated exchange rate and fromthe memory associated with the collection smart contract and to thedigital token holder associated with the second user computing device, asecond amount of the digital tokens.
 10. The method of claim 8, furthercomprising: registering, based on a second registration request receivedfrom the first device, a distribution smart contract by adding a secondnew block to the blockchain, wherein the second new block comprises thedistribution smart contract; transferring, based on a fourth eventmessage received from the first user device, a third amount of digitaltokens from a digital token holder associated with the first usercomputing device and to a memory associated with the distribution smartcontract; transferring, based on a fifth event message received from athird user computing device, a first amount of credit tokens from acredit token holder associated with the third user computing device andto the memory associated with the distribution smart contract, the firstamount of the credit tokens; and transferring, based on a digital tokenexchange rate, a fourth amount of digital tokens from the memoryassociated with the distribution smart contract and to a digital tokenholder associated with the third user computing device.
 11. The methodof claim 10, further comprising: based on a sixth event message receivedfrom the third computing device: transferring, based on a digital tokeninterest rate and a duration between receipt of the fifth event messageand the sixth event message, at least an additional amount of credittokens from the memory associated with the distribution smart contractand to the credit token holder associated with the third user computingdevice; and transferring, from the digital token holder associated withthe third user computing device and to the memory associated with thedistribution smart contract, a fifth amount of the digital tokenscorresponding to the digital token interest rate.
 12. The method ofclaim 11, further comprising: transferring, based on a determinationthat the fifth amount of the digital tokens does not correspond to anexpected amount of the digital tokens, the first amount of the credittokens from the memory associated with the distribution smart contractto a credit token holder associated with the first user computingdevice.
 13. The method of claim 10, further comprising: transferring,based on the second event message, a portion of the first amount of thedigital tokens from the memory associated with the collection smartcontract and to the distribution smart contract.
 14. The method of claim10, further comprising: determining, based on a credit score associatedwith the third user computing device, a second amount of the credittokens; and assigning the second amount of the credit tokens to thecredit token holder associated with the third user computing device. 15.One or more non-transitory computer readable media storing instructionsthat, when executed by a computing platform configured to operate in adecentralized peer-to-peer (P2P) network, the computing platformincluding one or more processors and memory storing at least a portionof a blockchain of the decentralized P2P network, cause the computingplatform to: register, based on a first registration request from afirst user computing device, a collection smart contract by adding afirst new block to the blockchain, wherein the first new block comprisesthe collection smart contract; authenticate a first event message basedon a digital signature associated with the first user computing device,wherein the first event message is received from the first usercomputing device and comprises an indication of a first amount ofservice provider tokens; transfer, from a service provider token holderassociated with the first user computing device and to a memoryassociated with the collection smart contract, the first amount of theservice provider tokens; authenticate a second event message receivedfrom a second user computing device based on a second digital signatureassociated with the second user computing device; and based on thesecond event message: transfer, from a digital token holder associatedwith the second user computing device and to the memory associated withthe collection smart contract, a first amount of the digital tokens; andtransfer, based on a digital token exchange rate and from the memoryassociated with the collection smart contract and to a service providertoken holder associated with the second user computing device, a secondamount of the service provider tokens.
 16. The one or morenon-transitory computer readable media of claim 15, wherein theinstructions, when executed by the computing platform, further cause thecomputing platform to: based on a third event message received from thesecond computing device: transfer, from the service provider tokenholder associated with the second user computing device and to thememory associated with the collection smart contract, a third amount ofthe service provider tokens; determine an updated exchange rate betweenthe digital tokens and the service provider tokens; and transfer, basedon the updated exchange rate and from the memory associated with thecollection smart contract and to the digital token holder associatedwith the second user computing device, a second amount of the digitaltokens.
 17. The one or more non-transitory computer readable media ofclaim 15, wherein the instructions, when executed by the computingplatform, further cause the computing platform to: register, based on asecond registration request received from the first device, adistribution smart contract by adding a second new block to theblockchain, wherein the second new block comprises the distributionsmart contract; transfer, based on a fourth event message received fromthe first user device, a third amount of digital tokens from a digitaltoken holder associated with the first user computing device and to amemory associated with the distribution smart contract; transfer, basedon a fifth event message received from a third user computing device, afirst amount of credit tokens from a credit token holder associated withthe third user computing device and to the memory associated with thedistribution smart contract, the first amount of the credit tokens; andtransfer, based on a digital token exchange rate, a fourth amount ofdigital tokens from the memory associated with the distribution smartcontract and to a digital token holder associated with the third usercomputing device.
 18. The one or more non-transitory computer readablemedia of claim 17, wherein the instructions, when executed by thecomputing platform, further cause the computing platform to: based on asixth event message received from the third computing device: transfer,based on a digital token interest rate and a duration between receipt ofthe fifth event message and the sixth event message, at least anadditional amount of credit tokens from the memory associated with thedistribution smart contract and to the credit token holder associatedwith the third user computing device; and transfer, from the digitaltoken holder associated with the third user computing device and to thememory associated with the distribution smart contract, a fifth amountof the digital tokens corresponding to the digital token interest rate.19. The one or more non-transitory computer readable media of claim 18,wherein the instructions, when executed by the computing platform,further cause the computing platform to: transfer, based on adetermination that the fifth amount of the digital tokens does notcorrespond to an expected amount of the digital tokens, the first amountof the credit tokens from the memory associated with the distributionsmart contract to a credit token holder associated with the first usercomputing device.
 20. The one or more non-transitory computer readablemedia of claim 17, wherein the instructions, when executed by thecomputing platform, further cause the computing platform to: determine,based on a credit score associated with the third user computing device,a second amount of the credit tokens; and assign the second amount ofthe credit tokens to the credit token holder associated with the thirduser computing device.